Seeing Organizations as Fluid Systems

Those tidy org charts pinned to conference room walls? They lie. Boxes and dotted lines paint a picture of a static machine, but anyone who has spent a Tuesday morning untangling a cross-team delay has felt the truth in their gut: work flows, stalls, and sometimes crashes in ways that feel oddly physical. I stumbled onto this idea years ago while neck-deep in both distributed systems and an old fluids textbook. Fluid dynamics—the study of how liquids and gases slosh, stream, and swirl—hands us a surprisingly sharp lens for diagnosing why some teams hum and others grind. Words like turbulence, viscosity, and boundary layers aren’t just poetry here. They map onto organizational life with a precision that feels almost unfair.

I’m Declan Mercier, and I’ve spent an unreasonable amount of time poking at these parallels. The interesting question isn’t whether a company resembles a river or a pipe network. It’s what happens when we take the resemblance seriously enough to redesign how we handle collaboration, decision speed, and the quiet art of not falling apart under pressure.

Viscosity: The Thickness of Bureaucracy

In a fluid, viscosity measures resistance to deformation. Honey oozes; water races. Inside an organization, viscosity is the friction that information and decisions hit as they try to move. Every approval layer, every meeting that should have been a two-line email, every fuzzy ownership boundary adds a tiny drag coefficient. One viscous step? Negligible. But string ten handoffs together and the cumulative drag turns a once-nimble process into something that barely budges.

The maddening thing about organizational viscosity is its patchiness. A marketing team might run with near-zero internal friction, yet every touchpoint with legal or finance feels like pushing cold molasses uphill. Measuring it isn’t clean, but you can spot the signals: time-to-decision on cross-functional work, the number of clarification emails pinging after a handoff, the ratio of synchronous meetings to things that get resolved quietly and asynchronously. Reducing viscosity usually means shrinking the gap between expertise and authority. Not always flattening hierarchies, but making sure the person who actually understands the problem can act without cycling through three layers of relay.

The Reynolds Number and the Onset of Turbulence

Fluid dynamicists lean on the Reynolds number to predict whether a flow stays laminar—smooth, predictable, layered—or goes turbulent, full of chaotic eddies and cross-currents. The number depends on velocity, a characteristic length scale, and viscosity. Translate that: velocity is the pace of work and change; characteristic length is the size of the org or the sprawl of a project; viscosity is that internal friction we just talked about.

Below some threshold, everything is laminar. A five-person startup coordinates without formal process because its Reynolds number is tiny. Then the company scales—more bodies, faster product cycles, offices in three time zones—and the number climbs. At some point, turbulence stops being a maybe and becomes a when. Eddies form: rumors swirl, teams duplicate effort, priorities smash into each other. The gut reaction is often to clamp down, add process, tighten control. But the physics whispers a different lesson. Turbulence isn’t a broken state; it’s a natural regime with its own rules. In turbulent flow, mixing happens fast. Ideas ricochet. The trick isn’t to stamp out turbulence but to build containers that channel it into something useful instead of something that just shreds morale.

Boundary Layers: Where the Real Friction Lives

When a fluid streams past a solid surface, a thin boundary layer hugs the wall where the velocity drops to nearly zero. The bulk of the fluid might barrel along unimpeded, but right at that interface, friction owns everything. Organizations grow boundary layers too: the seam between engineering and product, between headquarters and a regional outpost, between the exec team and everybody else. In these skinny zones, momentum dies. A strategic directive that sparkles in the C-suite hits the boundary layer and slows, twists, or just stops moving.

Boundary layer theory tells you that you can’t erase these interfaces—they appear wherever two different “materials” press against each other. But you can manage them. Smoothing a boundary layer means softening the abruptness of the transition. Maybe you embed liaisons, rotate people across functions, or co-locate teams that need to swap information at high frequency. It also means watching the thickness of the layer. A thick boundary layer—picture a multi-step translation ritual between a data science crew and a business unit—hints that the two sides have drifted too far apart, their vocabularies and rhythms diverging into separate dialects.

Pressure Gradients and the Direction of Flow

Fluids move from high pressure to low pressure. In a pipe, a pump sets that gradient. In a company, the gradient gets shaped by incentives, recognition, and the emotional gravity of different kinds of work. If the “pressure” peaks around firefighting production outages and barely registers for long-term architecture improvements, the flow of talent and attention will stampede toward the urgent and skirt the important. You can exhort people to “be strategic” until you’re hoarse; if the pressure gradient points the other way, the flow won’t budge.

This explains why some initiatives never catch. The pressure differential just isn’t there. Creating flow toward a new priority usually demands either cranking up the pressure on one side (making the current state genuinely uncomfortable) or easing it on the other (lowering the friction and risk of the new behavior). Fluid dynamics nudges us toward a humbling truth: flow isn’t about pushing harder everywhere. It’s about designing the right differential.

Practical Design Principles from Flow

So what shifts when we stop treating organizational design like architecture and start treating it like pipe engineering? A few principles bubble up, rooted in the physics of movement rather than management platitudes.

1. Smooth the Pipe Before Increasing the Pump

When flow slogs, the first impulse is often to crank up the pressure—more deadlines, more check-ins, more manufactured urgency. But if the pipe is rough with needless approvals, murky roles, or conflicting metrics, raising the pressure just whips up turbulence and raises the odds of something bursting. Smoothing the pipe means stripping out internal friction first. Take one cross-functional workflow and trace it end-to-end. Count the handoffs, the wait states, the decision gates. Each one is a roughness element. Chop the count by even 30% and you’ll often see throughput jump without anyone working longer or harder.

2. Match the Channel to the Expected Reynolds Number

Small teams can flourish in open, unstructured channels because their Reynolds number stays low. Larger organizations have to accept that turbulence is coming and build structures that steer it. This might mean creating semi-autonomous units that keep their local Reynolds number manageable while the whole system operates in a turbulent regime. Think of it as the organizational version of a multi-channel river delta: no single channel shoulders the full force of the flow, so the system stays navigable even when the floods come.

3. Monitor Boundary Layer Thickness

Boundary layers thicken over time as groups cultivate their own jargon, tools, and daily rhythms. A quarterly pulse check across key interfaces can catch dangerous thickening before it hardens into something immovable. Ask: how many translation steps does it take for an idea to travel from team A to team B and back? If the answer tops two, the boundary layer is probably too thick. Rotate a person, co-locate a project, or build a shared artifact that both sides feed and draw from.

4. Design Pressure Gradients Intentionally

Leaders often underestimate their role as pump designers. The incentives, public nods of recognition, and implicit signals they send out set the pressure landscape. If long-term thinking genuinely matters, the gradient has to reflect that—maybe through dedicated slack time, funding models that reward patience, or promotion criteria that weigh sustained impact above heroic last-minute saves. Without an intentional gradient, the flow follows the path of least resistance, which almost always dumps straight into the inbox.

The Limits of the Analogy

No analogy holds forever, and fluid dynamics won’t either. Organizations are made of humans—agents with opinions, moods, and a talent for reinterpreting signals in ways water molecules never will. A pressure gradient that feels manipulative can trigger resistance, not flow. Turbulence that might be productive in a fluid can curdle into toxic stress if a team lacks psychological safety. The physics gives us a starting point for diagnosis, not a tidy blueprint.

Still, the framework earns its keep by making certain dynamics legible. When a reorg feels like chaos, it helps to recognize that the system may have simply crossed its critical Reynolds number and entered a turbulent regime that needs new containers, not a nostalgic retreat to the old ones. When a strategy stalls, hunting for the boundary layer that swallowed its momentum is often more productive than second-guessing the strategy itself.

Flow as a Design Discipline

Organizational design has long borrowed from mechanical metaphors—levers, gears, alignment. Fluid metaphors yank the focus from static structure to dynamic movement. They ask not just “who reports to whom?” but “how fast does information travel, where does it pool, and what makes it swirl?” For anyone who has felt the weird physics of a large company—the way a minor decision can suddenly accelerate, or a critical initiative can mysteriously slow—the language of flow offers something rare: a way to glimpse the invisible currents that shape the daily grind.

Frequently Asked Questions

How is organizational viscosity different from simple bureaucracy?
Viscosity is the felt friction of bureaucracy, but it’s more pointed. You can have rules and processes that don’t add much viscosity if they’re well-understood and fast to execute. Viscosity measures the drag per interaction, which means a single approval step might be high-viscosity (demands a long meeting, ambiguous criteria) or low-viscosity (a quick automated check). Bureaucracy is the apparatus; viscosity is the resistance it creates.

Can an organization be too laminar?
Absolutely. A perfectly laminar organization—smooth, predictable, zero cross-currents—can turn brittle. In fluid dynamics, laminar flow is efficient but mixes terribly. An organization that never tastes healthy turbulence may struggle to cook up new ideas or flex when the outside world jolts. Some turbulence, in the form of constructive friction, cross-team collisions, and unplanned interactions, is essential for innovation and the ability to bounce back.

What’s a quick diagnostic for boundary layer problems?
Look for the number of “translation” activities between two groups. If team A produces a report that team B then interprets, summarizes, and re-presents to team C, you’ve spotted a thick boundary layer. Another signal: how often do people say “what they really mean is…” when relaying information from another department? That translation labor is the boundary layer at work, and it usually signals that the interface needs redesign, not more translators.